Skip to content

perf(uno-sample): measure Android cold start with startup markers - #295

Open
michaelstonis wants to merge 1 commit into
mainfrom
perf/278-uno-android-cold-start
Open

michaelstonis wants to merge 1 commit into
mainfrom
perf/278-uno-android-cold-start

Conversation

@michaelstonis

@michaelstonis michaelstonis commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

Closes #278.

The 15 to 20 s cold start did not reproduce. On the KumikoUI-MAUI-Android AVD (Android 35 arm64, 4 cores, 2 GB) the Uno sample's Release build started in a median of 2.16 s (am start -W, 7 cold starts) against 1.13 s for the MAUI sample. The extra second is Uno runtime startup and the NavigationView shell; KumikoUI's share (font registration about 15 ms, grid page and data about 70 ms, first paint) is small. Details are recorded under F8 in docs/uno/verification.md (in #298).

This adds startup markers to the sample's Android head (StartupTrace, logcat tag KumikoStartup, milliseconds since process start), compiled on Android only, so the measurement can be repeated on a device.

No physical device was measured.

StartupTrace logs the time since process start under the KumikoStartup logcat tag at the app, window and first page steps, so a cold start can be split without a profiler. It writes nothing on the other heads.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

Uno Android: Release cold start takes 15-20 s on the emulator

1 participant